Revisiting content history

ABSTRACT

The content items presented to a user account as part of a media station can be recorded in a content history index, which can be requested and presented to the user account. The content history can enable a user to revisit the content items included in the content history and/or provide feedback regarding the content items. The version of the content item returned to the user can be based on the client device used to request the content item. For example, a user that was presented a content item on their mobile device, can later request to revisit the content item on their PC and receive a version of the content item best suited for presentation by the PC, rather than the version presented on the mobile device.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims the benefit ofpriority to, U.S. application Ser. No. 14/186,965, filed on Feb. 21,2014, which is expressly incorporated by reference herein in itsentirety.

TECHNICAL FIELD

The present disclosure relates to recording a content history and morespecifically to revisiting content items listed in the content history.

BACKGROUND

Invitational content items such as advertisements have commonly beenpresented alongside traditional media, such as television and radio. Dueto the nature of traditional media, the advertisements presented havenot provided an interactive experience in which a user can engage withthe advertisement to select further information or to make an immediatepurchase.

The internet, in contrast, allows for media rich interactiveadvertisements that allow a user to request further information, accesssecondary information, etc. While these advertisements provide muchgreater functionality, a user is not always in an appropriate setting tointeract with the advertisement to fully appreciate everything that isoffered. For example, a user streaming a media stream while driving maynot be able to interact with their mobile device to properly engage withthe advertisement. Likewise, a user on a mobile device with a smallerdisplay may wish to interact with the advertisement when using theirdesktop, laptop or tablet Personal Computer (PC) that provides a muchlarger display.

Currently, a user has no way of re-accessing an advertisement that waspresented to the user. For example, a user unable to interact with anadvertisement presented while driving cannot access the advertisement ata more convenient to engage with the advertisement. As a result, usersmiss out on information that they are interested in and advertisers getless value from their marketing efforts.

SUMMARY

Additional features and advantages of the disclosure will be set forthin the description which follows, and in part will be obvious from thedescription, or can be learned by practice of the herein disclosedprinciples. The features and advantages of the disclosure can berealized and obtained by means of the instruments and combinationsparticularly pointed out in the appended claims. These and otherfeatures of the disclosure will become more fully apparent from thefollowing description and appended claims, or can be learned by thepractice of the principles set forth herein.

Disclosed are systems, methods, and non-transitory computer-readablestorage media for revisiting content items included in a contenthistory. A content item can include any type of content presented aspart of the media station, such as media items, buffer content items andinvitational content items. The content items presented to a user aspart of a media station can be recorded in a content history. Forexample, a content history index can be maintained that includes contentitem identifiers identifying content items presented to the user. Theuser can request their content history, which can be gathered from thecontent history index. The content history can be presented to enablethe user to select to revisit any of the content items previouslypresented to the user that are listed in the content history. Forexample, a user can select a content item presented in the contenthistory, causing a content request to present the content item to betransmitted and the content item being returned and presented to theuser.

In some embodiments, the version of the content item returned to theuser can be based on the client device used to request the content item.For example, a user that was presented a content item on their mobiledevice, can later request to revisit the content item on their PC andreceive a version of the content item best suited for presentation bythe PC, rather than the version presented on the mobile device. A usercan thus, request to revisit a content item on a client device of theirchoice and be presented with a version of the content item best suitedfor the selected client device.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and otheradvantages and features of the disclosure can be obtained, a moreparticular description of the principles briefly described above will berendered by reference to specific embodiments thereof which areillustrated in the appended drawings. Understanding that these drawingsdepict only exemplary embodiments of the disclosure and are nottherefore to be considered to be limiting of its scope, the principlesherein are described and explained with additional specificity anddetail through the use of the accompanying drawings in which:

FIG. 1 exemplary system configuration 100 in which multiple computingdevices can be configured to communicate with each other to create andperform a media station on a client device;

FIG. 2 illustrates an exemplary embodiment of recording a contenthistory;

FIG. 3 illustrates an exemplary method embodiment of revisiting contentitems presented in a content history;

FIG. 4 illustrates an exemplary embodiment of a content historypresented on a client device; and

FIG. 5A and FIG. 5B illustrate exemplary possible system embodiments.

DETAILED DESCRIPTION

Various embodiments of the disclosure are discussed in detail below.While specific implementations are discussed, it should be understoodthat this is done for illustration purposes only. A person skilled inthe relevant art will recognize that other components and configurationsmay be used without parting from the spirit and scope of the disclosure.

The disclosed technology addresses the need in the art for revisitingcontent items included in a content history. A content item can includeany type of content presented as part of the media station, such asmedia items, buffer content items and invitational content items. Thecontent items presented to a user as part of a media station can berecorded in a content history. For example, a content history index canbe maintained that includes content item identifiers identifying contentitems presented to the user. The user can request their content history,which can be gathered from the content history index. The contenthistory can be presented to enable the user to select to revisit any ofthe content items previously presented to the user that are listed inthe content history. For example, a user can select a content itempresented in the content history, causing a content request to presentthe content item to be transmitted and the content item being returnedand presented to the user.

In some embodiments, the version of the content item returned to theuser can be based on the client device used to request the content item.For example, a user that was presented a content item on their mobiledevice, can later request to revisit the content item on their PC andreceive a version of the content item best suited for presentation bythe PC, rather than the version presented on the mobile device. A usercan thus, request to revisit a content item on a client device of theirchoice and be presented with a version of the content item best suitedfor the selected client device.

FIG. 1 illustrates an exemplary system configuration 100 in whichmultiple computing devices can be configured to communicate with eachother to create and perform a media station on a client device. A mediastation can be a sequence of media items that can be played or executedby a media station player application on a client device. Somenon-limiting example of media items can include songs, podcasts,television shows, movies, games, audiobooks, educational courses, and/orvideo. Media items can also include live broadcasts such as traffic,weather, news, sports, music festivals, etc., streamed in real time.Other media items are also possible. A media station player can be anyapplication capable of media item playback, such as a component of awebpage, a plug-in, a client-side application, etc.

In some embodiments, a media station can be a continuous sequence ofmedia items such that as one media item completes playback a next mediaitem begins. The playback process of a continuous media item stream canrepeat until a user takes an action to terminate or temporarily delaythe playback, such as quitting the media player application, switchingto a different media station, pausing playback, or skipping a mediaitem. However, a media station can also be defined to be a finitesequence of media items. A media station can be homogeneous orheterogeneous. That is, a media station can be designed to playbackmedia items all of the same media type or of different media types. Forexample, a homogeneous media station can playback only audio media itemsor only video media items. As another example, a homogenous mediastation can playback only pre-recorded media items or, alternatively,only media items that are streamed live, such as a continuous live musicfestival. A heterogeneous media station can playback a mix of audiomedia items and video media items. As another example, a heterogeneousmedia station can playback a mix of live and pre-recorded media items,such as pre-recorded songs mixed with live news and traffic updates. Insome embodiments, the various media items can be presented concurrentlysuch that presentation of one media item overlaps with presentation witha different media item.

A media station can also be configured to play or present invitationalcontent, such as advertisements, within the media stream. Aninvitational content item can include content found in a media item,such as a song or a video, but an invitational content item can alsoinclude targeted content and/or content designed to elicit a responsefrom a user. Therefore an invitational content item and a media item canbe distinct item types, each of which can be presented in a mediastation.

In some embodiments, the invitational content can be used as a source ofrevenue and/or to subsidize a media station so that the media items canbe provided to end users free of charge or for a reduced fee. Theinvitational content can be presented within a media station using avariety of techniques. In some cases, invitational content can bepresented to a user in a manner that prevents or blocks the playback ofa next media item or a next segment of a media item. For example, uponthe completion of the playback of a music item, but before beginningplayback of a new music item, an invitational content item can bepresented in the media stream. Invitational content can also bedisplayed in conjunction with a media item or media item representation.For example, an invitational content item can be presented in a bannerad displayed with a music album cover or during the playback of atelevision show.

Further, in some embodiments, the invitational content can include aninteractive segment that can be presented concurrently with one or moremedia items. The interactive segment can be configured such that a usercan interact with the invitational content without disrupting playbackof media items being presented concurrently. A user can thus interactwith various features and views of the interactive segment during theplayback of a media item without disrupting the media item. For example,in some embodiments, the interactive segment can be a rich mediaadvertisement that includes various views and screens which a user cannavigate through while listening to an audio media item.

A downside to presenting both invitational content and media items,either simultaneously or sequentially, when the invitational content isnot related to the media items is that a user may equate the media itemwith the invitational content. For example, a user may think that aninvitational content provider endorses a particular media item, or thata media item provider has authorized the use of the media item topromote an offering associated with the invitational content. Todecrease the potential for confusion, the media station can also includebumper content, which can be presented concurrently with the interactiveinvitational content, but just prior to resuming playback of a mediaitem.

A bumper content item can be an intermediary content item that is usedto transition from invitational content to a media item, therebycreating user awareness that the media item is not related to an item ofinvitational content that the user may also be experiencing. Forexample, a bumper content item can be an audio message such as “now backto the music” that is used to transition between invitational content toan audio media item. Thus a user that is interacting with theinteractive segment of an item of invitational content will be madeaware that the upcoming media item is not related to the item ofinvitational content, even though the user is experiencing bothconcurrently.

To facilitate providing a media station to be performed by a clientdevice, multiple computing devices can be connected to a communicationnetwork 110 and configured to communicate with each other through use ofthe communication network 110. The communication network 110 can be anytype of network, including a local area network (“LAN”), such as anintranet, a wide area network (“WAN”), such as the internet, or anycombination thereof. Further, the communication network 110 can be apublic network, a private network, or a combination thereof. Thecommunication network can also be implemented using any type or types ofphysical media, including wired communication paths and wirelesscommunication paths associated with one or more service providers.Additionally, the communication network 110 can be configured to supportthe transmission of messages formatted using a variety of protocols.

A computing device can be any type of general computing device capableof network communication with other computing devices. For example, thecomputing device can be a personal computing device such as a desktop orworkstation, a business server, or a portable computing device, such asa laptop, smart phone, or tablet personal computer. The computing devicecan include some or all of the features, components, and peripherals ofcomputing device 500 of FIGS. 5A and 5B.

To facilitate communication with other computing devices, the computingdevice can also include a communication interface configured to receivea communication, such as a request, data, etc., from another computingdevice in network communication with the computing device and pass thecommunication along to an appropriate module running on the computingdevice. The communication interface can also be configured to send acommunication to another computing device in network communication withthe computing device.

As illustrated, a client device 105 can be configured to communicatewith a media station server 125 to perform a media station on the clientdevice 105. For example, a media player application 115 running on theclient device 105 can be configured to communicate with a media stationmodule 130 on the media station server 125 to request, receive andperform a media station. A media station player can be any applicationcapable of media item playback, such as a component of a webpage, aplug-in, a client-side application, etc.

The media station module 130 can be configured to create a media stationto be performed on a client device. For example, the media stationmodule 130 can be configured to assemble the media station by selectingmedia items, invitational content items and bumper items to be performedon the client device in a specified order. For example, the mediastation server 125 can include a media item database 135, a bumpercontent database 145 and an invitational content database 150, eachconfigured to store multiple media items, bumper content items, andinvitational content items respectively. The media station module 130can be configured to communicate with the databases to select mediaitems, bumper content items and invitational content to be performed aspart of the media station.

Although the media item database 135, bumper content database 145 andthe invitational content database 150 are illustrated separately, thisis just one possible embodiment and is not meant to be limiting. In someembodiments, the databases can be combined as one database or any otherpossible combination.

Alternatively, in some embodiments, the multiple databases can be hostedon separate computing devices and the media station module 130 can beconfigured to communicate with the various computing devices to assemblethe media station. For example, in some embodiments, the system caninclude an invitational content server 170 in network communication withthe media station server 125 and the media station module 130 can beconfigured to communicate with the invitational content server 170 torequest invitational content to be included in the media station. Insome embodiments, the invitational content server 170 can transmit theinvitational content to the media station server 125 where it can beassembled into the media station. In some embodiments, the invitationalcontent server 170 can transmit the invitational content directly to theclient device 105.

In some embodiments, the media station module 130 can be configured totransmit the assembled media station to the client device 105 where itcan be performed by the media player application 115. For example, themedia station module 130 can be in continuous communication with themedia player application 115 to transmit the media station to beperformed by the media player application 115.

In some embodiments, the media station module 130 can be configured totransmit the media station to the client device 105 in segments. Forexample, the media station module 130 can be configured to communicatewith the client device to transmit an assembled segment of the mediastation which can be stored on the client device 105 and performed bythe media player application 115. For example, the client device 105 caninclude a media station database 120 configured to store the receivedmedia station and the media player application 115 can be configured tocommunicate with the media station database 120 to retrieve the storedmedia station. In this type embodiment, the media station module 130 canbe configured to periodically update the client device 105 bytransmitting further assembled segments of the media station.

In some embodiments, the media station can be assembled at the clientdevice 105 rather than at the media station server 125. For example, themedia station module 130 can be running on the client device 105 and canbe configured to request media items, bumper content items andinvitational content from the media station server 125, or any othercomputing device. The received media items, bumper content items andinvitational content items can be stored in the media station database120 and the media station module 130 can be configured to communicatewith the media station database 120 to retrieve the stored media items,bumper content items and invitational content to assemble the mediastation. In this type of embodiment, the media station module 130running on the client device 105 can be configured to periodicallyrequest further media items, bumper content items and invitationalcontent be delivered to the client device.

The media station module 130 can be configured to assemble the mediastation based upon media station assembly rules. The media stationassembly rules can dictate which media items, invitation content itemsand bumper content items should be selected for the media station aswell as the sequential order in which they should be presented by themedia player application 115.

In some embodiments, media station server 125 can be configured tomaintain a content history of the content items presented to a useraccount as part of a media station or media station(s). The contentpresented to a user account can include media items, bumper contentitems and invitational content items presented to the user account.Media station server 125 can include content history module 155configured to record the content history for user accounts. This caninclude detecting when a content item has been presented to a clientdevice associated with or authorized to access the user account andrecording that the content item has been presented to the user account.

To record the content history for a user account, content history module155 can maintain a content history index that identifies the contentitems that have been presented to the user account. For example, thecontent history index can include a separate entry for each content itempresented to the user account. Each entry in the content history indexcan include a content item identifier that uniquely identifies thecontent item that was presented to the user account. Alternatively, thecontent item identifier can identify a group of related content items,such as content items from the same artist, advertisers, sameadvertisement campaign, etc.

Media station server 125 can include content history database 160configured to store content history indexes for multiple user accounts.Upon detecting that a content item has been presented to a user account,content history module 155 can be configured to access the appropriatecontent history index in content history index database 160, and add anew entry to the content history index that includes a contentidentifier identifying the content item that was presented to the useraccount.

To determine the appropriate content history index in which to recordpresentation of the content item, content history module 155 canidentify the user account that the content item was presented to andaccess the content history index associated with the user account. Insome embodiments, media station server 125 can require that a clientdevice be authorized to access a user account as a prerequisite torequesting and receiving a media station. This can include providinglogin credential to access an existing user account or creating a newuser account. Content history module 155 can determine the user accountthat the client device is authorized to access, and then access thecontent history index associated with the user account in contenthistory database 160.

Alternatively, in some embodiments, media station server 125 may notrequire a user to create a user account. Rather, one or more clientdevices can be associated with each other to create a user accountwithout user input. For example, media station server 125 can determinethat one or more client devices are associated with the same user. Thus,the one or more client devices can be associated with an anonymous useraccount.

Content history module 155 can identify the appropriate content historyindex from the client devices associated with the user account thatpresented the content. For example, user account data associated witheach user account can include one or more client device identifiersidentifying client devices associated with the user account. Contenthistory module 155 can identify the client device that received theinvitational content item and determine the user account associated withthe client device from the user account data.

In some embodiments, the content history index can include othermetadata describing presentation of the content items. For example, eachentry in the content history index can include metadata describing thecontent item (name, advertiser, advertisement campaign, artist, album,descriptive text, images, etc.), identifying the time the content itemwas presented, the client device that presented the content item,detected interaction with the content item, location of the clientdevice when the content item was presented, etc. Content history module155 can then gather this metadata from the client device and/orcomponents and databases of media station server 125 and record themetadata in the content history index.

Content history module 155 can also be configured to provide a useraccount with the user account's content history. For example, contenthistory module 155 can be configured to receive a content historyrequest from client devices 102, and provide the appropriate contenthistory in response to the content history request. This can includeidentifying the user account associated with the content historyrequest, accessing the corresponding content history index, andtransmitting the content history to the requesting client device.

In some embodiments, content history module 155 can return the entirecontent history. Alternatively, in some embodiments, content historymodule 155 can select a subset of the user account's content history toreturn. For example, content history module 155 can select the subset ofthe content history to return based on time. Content history module 155can select the content items presented to the user account within apredetermined amount of time prior to receiving the content historyrequest, such as the previous hour, day, week, month, etc.

Alternatively, content history module 155 can select a subset of thecontent history to return based on content type. For example, contenthistory module 155 can select from only the media items and invitationalcontent item that were presented at devices associated with the useraccount.

In some embodiments, content history module 155 can select a subset ofthe content history to return based on preferences provided by a user.In some embodiments, the preferences can be stored content historydatabase 160 and associated with the content history index associatedwith the user account. Content history module 155 can access thepreferences and select a subset of the content history according to theprovided preferences.

In some embodiments, a user can provide preferences dictating the typesof content the user would like to be presented in their content history.Alternatively, the user can select a date or time range for the contenthistory. For example, the user can select to only receive the contenthistory for the previous hour, day, week, etc. Content history module155 can select the subset of the content history based on the userprovided preferences.

In some embodiments, content history module 155 can select a subset ofthe content history based on the requesting client device. For example,content history module 155 can select only the content items that arecapable of presentation by the requesting client device to include inthe content history.

In some embodiments, content history module 155 can select a subset ofthe content history based on a network connection being utilized by therequesting client device. For example, content history module 155 canselect to present only the content items that can be easily downloadedby the client device based on the network connection being utilized bythe client device. Thus, content history module 155 can select onlycontent items below a specified data size when the requesting clientdevice is utilizing a slower network connection such as 3G, and selectcontent items above the specified size if the client device is utilizinga faster network connection such as WiFi.

In some embodiments, content history module 155 can select the subset ofcontent items based on a set of rules provided by a content provider.For example, a content provider can provide a set of conditions thatmust be met for the content item to be included in the content history.For example, the content provider can dictate a network connection type,client device type, etc., that must be met for a content item to bepresented as part of a content history.

The content history provided in response to a content history requestcan include data identifying the content items presented to the useraccount, as well as metadata describing the content items. For example,the content history can include a name, time, description, image, etc.describing the content item in the content item history.

In some embodiments, the content history can be presented to a user inchronological order. For example, the content items can be presented inthe order in which they were presented to the client device.Alternatively, in some embodiments, the content history can be presentedto highlight one or more content item. For example, one select contentitem can be presented at the top of the content history in addition orinstead of in its chronological order within the content history.Alternatively, a select content item can be presented with a highlightedbackground or with some other type of graphical presentation to bringattention to the select content item.

A content item can be a select content for numerous reasons. Forexample, a content item from a new artist or an advertisement from afeatured sponsor can be select. Alternatively, the most recentlypresented advertisement can always be a select content item andpresented in a highlighted fashion, either in chronological order or atthe top of the content history.

Further, the content history can enable a user to revisit the contentitems included in the content history. For example, in some embodiments,content items presented in the content history can be presented asinteractive elements that, when selected, cause the content item to bepresented.

In some embodiments, the content history presented can be configured toallow a user to select to revisit any of the content items included inthe content history. Alternatively, in some embodiments, the contenthistory can be configured to allow a user to revisit only a subset ofthe content items included in the content history. For example, thecontent history can be configured to allow a user to only revisitcontent items of a specified type, such as only invitational contentitems. Alternatively, the content history can be configured to allow auser to only revisit content item presented within a predetermined timeprior to presentation of the content item history; for example, onlycontent items presented within the previous hour, day, week, etc.

To enable a user to revisit a content item included in the contenthistory, the content history can include the content item identifieridentifying the content item and, upon selection by a user to revisitthe content item, the content item history can cause the client devicerendering the content item history to transmit a content request tomedia station server 125 that includes the content item identifier. Uponreceiving the a content request, content history module 155 can identifythe content item identified by the content item identifier and returnthe identified content item to the requesting client device, where itcan be rendered. For example, content history module 155 can request thecontent item from invitational content server 170.

In some embodiments, a user can select a specific content item torevisit without first being presented with the content history. Forexample, a user can utilize a speech recognition component of a clientdevice 105 to request a specific content item based on when the contentitem was performed, content item type, title, etc. A user can thusverbally request to revisit the last content item performed, the lastadvertisement performed, the content item played 10 minutes ago, etc.,to request to revisit the described content item.

Client device 105 can be configured to transmit a content requestincluding the provided description to request the content item. Forexample, a content request can indicate that the user requested the lastadvertisement played. Content history module 155 can use the receivedmetadata to identify the corresponding content item based on themetadata stored in the content history index. Upon identifying theappropriate entry, content history module 155 can access the contentitem identifier included in the entry and transmit the content itemidentified by the content item identifier to the requesting clientdevice 105.

In some embodiments, content history module 155 can select a version ofthe content item to return in response to a content request based on therequesting client device. For example, content history module 155 canselect and return a version of the content type that is best suited forpresentation by the requesting client device. To accomplish this,content history module 155 can identify the type of the client devicefrom which the content request was received and select a version of therequested content item accordingly. In some embodiments, the contentrequest can include data identifying the client device type. In someembodiments, the client device type can be determined from data storedin a user profile associated with the user account.

In some embodiments, content history module 155 can select an alternatecontent item to return in response to a content request. For example, auser may select to revisit a content item that has since expired or beenremoved. For example, a content item such as an advertisement may onlybe available for a limited time, after which the advertisement expiresand can no longer be accessed. In this type of situation, contenthistory module 155 can select an alternate content item to present inresponse to the content request.

In some embodiments, the alternate content item can be selected based onthe requested content item. Metadata associated with the content itemcan be used to select the alternate content item. For example, thealternate content item can be selected from other content items from thesame advertiser, campaign, producer, artist, etc. Alternatively, thealternate content item selected can include similar content to therequested content item. For example, content history module 155 canselect an alternate content item that advertises a similar type ofproduct, service, etc., as the requested content item.

In some embodiments, the content history can enable a user to providefeedback regarding the content items. For example, the content historycan include user interface elements such as buttons, checkboxes, textboxes, etc., configured to enable to receive input from a user regardingthe content items. In some embodiments, the content history can enable auser to provide feedback indicating whether the user likes or dislikes acontent item. Alternatively, in some embodiments, the content historycan enable a user to enter whether the user would like to see more orless content items similar to a content item in the content history.

FIG. 2 illustrates an exemplary embodiment of recording a contenthistory. As shown, the method begins at block 205 where a content itemis provided to a client device. For example, the content item can beprovided as part of a media stream such as an online radio station,television station, etc., which can be presented by a media playerapplication on the client device. For example, the media player canrender any audio, video, code, etc., included in the invitationalcontent item to render the content item, which can include any of amedia item, bumper item or invitational content item.

Upon providing the content item to the client device, the methodcontinues to block 210 where a new entry is added to the appropriatecontent history index. Each user account can be associated with acontent history index that identifies the content items presented toclient devices authorized on the user account. For example, the contentitem index can include content item identifiers identifying the contentitems presented to the user account. A new entry in the content itemindex can be added that includes the invitational content itemidentifier identifying the content item presented to the user account.

In some embodiments, the entry in the content item index can alsoinclude other metadata describing the content item. For example, thecontent item index can include a title, artist, advertiser, image, etc.Further, the content item index can include metadata describing deliveryof the content item, such as the time the content item was delivered,the client device type that presented the content item, any detectedinteraction with the content item, etc. The method then ends.

FIG. 3 illustrates an exemplary method embodiment of revisiting contentitems presented in a content history. As shown, the method begins atblock 305 where a content history request is received. The contenthistory request can be a request for the content history associated witha user account. For example, a client device authorized to access theuser account can request to receive the content history for the useraccount by transmitting the content history request.

Upon receiving the content history request, the method continues toblock 310 where the content history index associated with the useraccount is identified. For example, the user account that the clientdevice is authorized to access can be identified and the correspondingcontent history index can be identified.

The method then continues to block 315 where the content history isreturned. This can include returning all or a subset of the dataincluded in the content history index. For example, the content historycan include data identifying each content item included in the contenthistory or, alternatively, a subset of the content items included in thecontent history.

In some embodiments, the content history can include only content itemsof a certain types, such as only invitational content items and mediaitems. Further, the content history can include only a subset of thecontent items based on time. For example, the content history caninclude the content items presented to the user account within the lasthour, day, week, etc.

The content history can include data identifying the content items aswell as metadata describing the content items, such as a title, image,description, etc. The content history can also be configured to allow auser to select to revisit one of the content items listed in the contenthistory. For example, in some embodiments, the content history can beconfigured to receive input enabling a user to select a content itemthat the user would like to revisit. Revisiting a content item can bepresentation of the content item on a client device of the user. Uponselection of a content item to be revisited, the content history cancause a client device to transmit a content request requesting theselected content item.

Upon returning the content history in response to the content historyrequest, the method continues to block 320 where it is determined if acontent request is received. For example, the content request can bereceived as a result of a user selecting to revisit a content itempresented in a content history. If at block 320 a content request isreceived, the method continues to block 325 where the requested contentitem is identified. In some embodiments, the content request can includethe content item identifier that identifies the requested content item.The received content item identifier can be used to identify therequested content item.

Further, in some embodiments, an appropriate version of the content itemcan be identified. The version of the content item can be selected basedon the requesting client device. For example, a version of the contentitem best suited to perform on the client device can be selected. Thiscan include selecting a mobile version of the content item for a mobileclient device. Alternatively, an enhanced version of the content itemcan be selected for client devices with capabilities to perform theenhanced capabilities, such as client devices with larger screens,increased computing capabilities, etc.

At block 330, the requested content item is returned in response to thecontent request. The method then continues to block 320, where, if acontent request is not received, the method ends.

FIG. 4 illustrates an exemplary embodiment of a content history 400presented on a client device. As shown, the content history identifiesthe six content items presented to a user between 11:35 am and 11:42 am.Each content item presented during that time span is represented by aseparate entry in content history 400. Each entry includes datadescribing the content item presented. For example. Entry 405 indicatesthat at 11:35 am, the song “Thriller” by Michael Jackson was presentedto the user. Further, entry 410 indicates that at 11:40 am,Advertisement #1 from Advertiser #1 was presented. Likewise, entry 415indicates that at 11:42 am, Advertisement #2 by Advertiser #2 waspresented to the user.

Although content history 400 is illustrated as only including the, time,author and title, this is only one possible embodiment and is not meantto be limiting. One skilled in the art would recognize that any metadatacan be included in the content history, such as the client device thecontent item was presented on, an image, a description, etc., and thisdisclosure contemplates all such embodiments.

As shown, entries 410 and 415 include a user interface element buttonenabling a user to request revisit the content item identified by therespective entry. For example, a user can select user interface element420 to revisit Advertisement #1 by Advertiser #1. Selection of userinterface element 420 can result in a content request being transmittedthat requests presentation of Advertisement #1, or some alternativethereof. Likewise, selection of user interface element 425 can result ina content request being transmitted that requests presentation ofAdvertisement #2, or some alternative thereof.

As shown, entry 405 does not include a user interface element enabling auser to revisit the content item. Thus, content history 400 is notconfigured to enable a user to revisit “Thriller” by Michael Jackson,although in other embodiments, each content item can be revisited.

Further each entry 405, 410 and 415, include feedback user interfaceelements that enable a user to provide feedback indicating whether theuser likes or dislikes the content item. For example, a user can selectuser interface element 430 to provide feedback that the user likes“Thriller” by Michael Jackson, which can result in this content itemand/or similar content items being presented to the user in the future.Likewise, a user can select user interface element 435 to indicate thatthe user does not like Advertisement #1, resulting in Advertisement #1and/or advertisement by Advertiser #1 not being presented to the user inthe future.

Although content history 400 is illustrated as only including userinterface elements to receive user feedback regarding whether the userlikes or dislikes a content item, this is only one possible embodimentand is not meant to be limiting. One skilled in the art would recognizethat content history 400 can be configured to enable a user to provideany of a variety of feedback regarding a content item, such as a rating,comments, indication to see more like this, indication to see less likethis, etc., and this disclosure contemplates all such embodiments.

FIG. 5A, and FIG. 5B illustrate exemplary possible system embodiments.The more appropriate embodiment will be apparent to those of ordinaryskill in the art when practicing the present technology. Persons ofordinary skill in the art will also readily appreciate that other systemembodiments are possible.

FIG. 5A illustrates a conventional system bus computing systemarchitecture 500 wherein the components of the system are in electricalcommunication with each other using a bus 505. Exemplary system 500includes a processing unit (CPU or processor) 510 and a system bus 505that couples various system components including the system memory 515,such as read only memory (ROM) 520 and random access memory (RAM) 525,to the processor 510. The system 500 can include a cache of high-speedmemory connected directly with, in close proximity to, or integrated aspart of the processor 510. The system 500 can copy data from the memory515 and/or the storage device 530 to the cache 512 for quick access bythe processor 510. In this way, the cache can provide a performanceboost that avoids processor 510 delays while waiting for data. These andother modules can control or be configured to control the processor 510to perform various actions. Other system memory 515 may be available foruse as well. The memory 515 can include multiple different types ofmemory with different performance characteristics. The processor 510 caninclude any general purpose processor and a hardware module or softwaremodule, such as module 1 532, module 2 534, and module 3 536 stored instorage device 530, configured to control the processor 510 as well as aspecial-purpose processor where software instructions are incorporatedinto the actual processor design. The processor 510 may essentially be acompletely self-contained computing system, containing multiple cores orprocessors, a bus, memory controller, cache, etc. A multi-core processormay be symmetric or asymmetric.

To enable user interaction with the computing device 500, an inputdevice 545 can represent any number of input mechanisms, such as amicrophone for speech, a touch-sensitive screen for gesture or graphicalinput, keyboard, mouse, motion input, speech and so forth. An outputdevice 535 can also be one or more of a number of output mechanismsknown to those of skill in the art. In some instances, multimodalsystems can enable a user to provide multiple types of input tocommunicate with the computing device 500. The communications interface540 can generally govern and manage the user input and system output.There is no restriction on operating on any particular hardwarearrangement and therefore the basic features here may easily besubstituted for improved hardware or firmware arrangements as they aredeveloped.

Storage device 530 is a non-volatile memory and can be a hard disk orother types of computer readable media which can store data that areaccessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs) 525, read only memory (ROM) 520, andhybrids thereof.

The storage device 530 can include software modules 532, 534, 536 forcontrolling the processor 510. Other hardware or software modules arecontemplated. The storage device 530 can be connected to the system bus505. In one aspect, a hardware module that performs a particularfunction can include the software component stored in acomputer-readable medium in connection with the necessary hardwarecomponents, such as the processor 510, bus 505, display 535, and soforth, to carry out the function.

FIG. 5B illustrates a computer system 550 having a chipset architecturethat can be used in executing the described method and generating anddisplaying a graphical user interface (GUI). Computer system 550 is anexample of computer hardware, software, and firmware that can be used toimplement the disclosed technology. System 550 can include a processor555, representative of any number of physically and/or logicallydistinct resources capable of executing software, firmware, and hardwareconfigured to perform identified computations. Processor 555 cancommunicate with a chipset 560 that can control input to and output fromprocessor 555. In this example, chipset 560 outputs information tooutput 565, such as a display, and can read and write information tostorage device 570, which can include magnetic media, and solid statemedia, for example. Chipset 560 can also read data from and write datato RAM 575. A bridge 580 for interfacing with a variety of userinterface components 585 can be provided for interfacing with chipset560. Such user interface components 585 can include a keyboard, amicrophone, touch detection and processing circuitry, a pointing device,such as a mouse, and so on. In general, inputs to system 550 can comefrom any of a variety of sources, machine generated and/or humangenerated.

Chipset 560 can also interface with one or more communication interfaces590 that can have different physical interfaces. Such communicationinterfaces can include interfaces for wired and wireless local areanetworks, for broadband wireless networks, as well as personal areanetworks. Some applications of the methods for generating, displaying,and using the GUI disclosed herein can include receiving ordereddatasets over the physical interface or be generated by the machineitself by processor 555 analyzing data stored in storage 570 or 575.Further, the machine can receive inputs from a user via user interfacecomponents 585 and execute appropriate functions, such as browsingfunctions by interpreting these inputs using processor 555.

It can be appreciated that exemplary systems 500 and 550 can have morethan one processor 510 or be part of a group or cluster of computingdevices networked together to provide greater processing capability.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

In some embodiments the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, and so on. Functionality described herein also can beembodied in peripherals or add-in cards. Such functionality can also beimplemented on a circuit board among different chips or differentprocesses executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

1-20. (canceled)
 21. A system comprising: at least one processor; atleast one storage device storing a content history index for a useraccount, the content history index including content item identifiersfor content items presented to client devices associated with the useraccount; and at least one memory storing instructions which whenexecuted by the processor cause the processor to: receive, from a secondclient device associated with the user account different than a firstclient device associated with the user account, a request for thecontent history of the user account, wherein the content historyincludes at least one content item presented to the first client deviceassociated with the user account in a version that is compatible withthe first client device; present, to the second client device, thecontent history; receive, from the second client device, a request torevisit the at least one content item presented to the first clientdevice selected from the content history; and present, to the secondclient device, the at least one content item presented to the firstclient device for playback, wherein the content item is presented in asecond version compatible with the second client device that isdifferent than the version compatible with the first client device. 22.The system of claim 21, further comprising instructions which whenexecuted by the processor causes the processor to: identify, based onthe content item identifier, one or more related content items; andprovide, at least one of the one or more related content items with thecontent item.
 23. The system of claim 21, wherein sending the contenthistory further comprises instructions which when executed by theprocessor causes the processor to: determine a subset of the contenthistory; and send the subset of the content history to the second clientdevice.
 24. The system of claim 23, wherein the subset of the contenthistory is based on a predetermined amount of time.
 25. The system ofclaim 23, wherein the subset of the content history is based on acontent type.
 26. The system of claim 21, wherein the content history issent in chronological order.
 27. The system of claim 21, wherein therequest for the content history of the user account is a verbal request.28. A non-transitory computer readable medium storing instructions,which when executed by a processor, causes the processor to: receive,from a second client device associated with a user account differentthan a first client device associated with the user account, a requestfor content history of the user account, wherein the content historyincludes at least one content item presented to the first client deviceassociated with the user account in a version that is compatible withthe first client device; present, to the second client device, thecontent history; receive, from the second client device, a request torevisit the at least one content item presented to the first clientdevice selected from the content history; and present, to the secondclient device, the at least one content item presented to the firstclient device for playback, wherein the content item is presented in asecond version compatible with the second client device that isdifferent than the version compatible with the first client device. 29.The non-transitory computer readable medium of claim 28, furthercomprising instructions which when executed by the processor causes theprocessor to: identify, based on the content item identifier, one ormore related content items; and provide, at least one of the one or morerelated content items with the content item.
 30. The non-transitorycomputer readable medium of claim 28, wherein sending the contenthistory further comprises instructions which when executed by theprocessor causes the processor to: determine a subset of the contenthistory; and send the subset of the content history to the second clientdevice.
 31. The non-transitory computer readable medium of claim 30,wherein the subset of the content history is based on a predeterminedamount of time.
 32. The non-transitory computer readable medium of claim30, wherein the subset of the content history is based on a contenttype.
 33. The non-transitory computer readable medium of claim 28,wherein the content history is sent in chronological order.
 34. Thenon-transitory computer readable medium of claim 28, wherein the requestfor the content history of the user account is a verbal request.
 35. Amethod for revisiting a content item, the method comprising: receiving,at a processor from a second client device associated with a useraccount different than a first client device associated with the useraccount, a request for content history of the user account, wherein thecontent history includes at least one content item presented to thefirst client device associated with the user account in a version thatis compatible with the first client device; presenting, to the secondclient device, the content history; receiving, at the processor from thesecond client device, a request to revisit the at least one content itempresented to the first client device selected from the content history;and presenting, to the second client device, the at least one contentitem presented to the first client device for playback, wherein thecontent item is presented in a second version compatible with the secondclient device that is different than the version compatible with thefirst client device.
 36. The method of claim 35, further comprising:identifying, by the processor and based on the content item identifier,one or more related content items; and providing at least one of the oneor more related content items with the content item.
 37. The method ofclaim 35, wherein sending the content history further comprising:determining a subset of the content history; and sending the subset ofthe content history to the second client device.
 38. The method of claim37, wherein the subset of the content history is based on apredetermined amount of time.
 39. The method of claim 37, wherein thesubset of the content history is based on a content type.
 40. The methodof claim 35, wherein the content history is sent in chronological order.